On the one hand, the filename templates look awesome:

sub-<label>/
    [ses-<label>/]
        meg/
            sub-<label>[_ses-<label>]_task-<label>[_acq-<label>][_run-<index>][_proc-<label>][_split-<index>]_meg.<extension>
            sub-<label>[_ses-<label>]_task-<label>[_acq-<label>][_run-<index>][_proc-<label>][_split-<index>]_meg.json
            sub-<label>[_ses-<label>]_acq-<calibration>_meg.dat
            sub-<label>[_ses-<label>]_acq-<crosstalk>_meg.fif
            sub-<label>[_ses-<label>][_task-<label>][_acq-<label>][_space-<label>]_markers.mrk
            sub-<label>[_ses-<label>][_task-<label>][_acq-<label>][_space-<label>]_markers.sqd
            sub-<label>[_ses-<label>]_task-<label>[_acq-<label>][_run-<index>]_events.json
            sub-<label>[_ses-<label>]_task-<label>[_acq-<label>][_run-<index>]_events.tsv

On the other hand, the entity tables look terrible:

"also meg" was the best I came up with 😞, and I just realized that the way I wrote the code, it can only handle two rows with the same datatype/suffixes, so... thoughts?

Can we name these files meg (shielding) or something similar? This goes for the calibration and crosstalk, right?

@guiomar there's no mechanism to label the different groups of suffixes in the schema at the moment. We could add one, though I'm always hesitant to add new fields to the schema.

EDIT: Yes, the new row corresponds to both calibration and crosstalk files.

As a more flexible, but not very informative, alternative, I've made it able to handle any number of duplicates and have dropped the "also":

thanks! looks all good except the entity table, as you say :-)

As a more flexible, but not very informative, alternative, I've made it able to handle any number of duplicates and have dropped the "also"

Can we not make it MEG (calibration & crosstalk) ?

Can we not make it MEG (calibration & crosstalk) ?

That would be fine with me.

The rest looks good. :-D

Can we not make it MEG (calibration & crosstalk) ?

@sappelhoff @Remi-Gau I can't think of a straightforward way to do that with the current schema, so I would need to add a new field, like "name", for labeling whole groups of suffixes in schema/rules/datatypes/*.yaml.

OK I am ok keeping like this for now

Hi! I think I missed when the calibration and crosstalk files were incorporated to the specs. I think they weren't on the first release. Why do they have the _meg suffix? Shouldn't it have been better to have something like shielding for a suffix to disentangle from actual meg data? These are only required for SSS in Elekta systems, right? Maybe some discussions related to that happened that I missed, sorry!

Maybe some discussions related to that happened that I missed, sorry!

it happened here @guiomar :-)

• [ENH] Specify how to share cross-talk and fine-calibration for Neuromag/Elekta/MEGIN data #581

Thanks @sappelhoff! And it's not that you didn't tag me!

Is everyone okay with me merging?